home *** CD-ROM | disk | FTP | other *** search
-
- OK.. here's a list of the known problems - I'm working on them, so unless
- you know how to help... please don't write to me about it!
-
- 1) Using a SB16 with DMA 1, causes floppy disk read errors when stereo is
- selected! I don't know *WHY* it does this, but when you turn OFF stereo,
- you can access your floppy disks again perfectly well!
-
- I suspect that this problem also causes problems with QEMM. (I haven't
- tested it myself)
-
- My only possible suggestion (and it sucks), is that there's a hardware
- fault on the SB16 for it's 8-bit DMA..... it doesn't seem to cause any
- obvious problems when I put my SB16 onto DMA 3, though.
-
- 2) Incompatibilities with some monitors (Which don't support the screen mode
- that I'm using) and video cards (which don't support a second character
- set). Also, a really weird fix for problems with the video mode (but one
- that works for the person who sent it to me) was to run DOS's EDIT before
- running the tracker!
-
- 3) Sound Blaster 2.00 users will find that the detection finds a SB Pro.
- Sorry - you'll have to override the commandline switch with -s1 for now.
-
- 4) Apparently, many problems have been encountered with QEMM... I really
- don't know what's going wrong here at the moment (I haven't had any
- experience with QEMM myself), but I would recommend that you steer clear
- of QEMM if possible for the meantime.
-
- 5) With the GUS, 16-bit samples > 256k will *NOT* be played correctly. This is
- due to a 'quirk' of the GUS - something that I don't know how to easily fix.
- This does *NOT* occur with 8-bit samples. (This is the same problem that
- you'll find in FastTracker II also)
-
- 6) Some MODs/S3Ms won't sound quite correct if they use G00 commands after
- Exx or Fxx commands, because in Impulse Tracker, the 'memory' for Exx, Fxx
- and Gxx are linked, whereas this is not so for MODs/S3Ms. Also, S3M also
- links Exx and Dxx (I *THINK*) whereas IT does *NOT*
-
- 7) The "Active Channels" indication is *NOT* always 100% accurate (it's
- even affected by stuff played in muted channels.....) Also, on a GUS, the
- program requires the GUS to provide the 'end of note indication', whereas
- the mixing routines are calculated internally... hence, if the GUS provides
- the indication a little later than expected, another channel is allocated
- - what this means is that the value as played on GUS cards *MAY* differ
- from the value played on software-mixed cards. This difference is minor
- (ie. 2 channels at most, unless you *TRY* to setup a special situation)
-
- 8) Due to the nature of the way I'm accessing memory, if you put a very small
- loop around multiples of 64k, then the program *WILL* slow down badly.
- This should not be a problem in general use, but is mentioned here just
- in case.... And don't just go and try it out to prove that it isn't the
- best routine :)
-
- 9) There is no 'enforce Amiga limits' option in IT (Which was in ST3) so
- pitches of notes exceeding the Amiga limit will not be suitably played.
-
- 10) If your system behaves unexpectedly in IT, it *MAY* be necessary to
- specify the complete parameter list on the command line. This should NOT
- be a problem in most cases, but it has been known to occur.
-
- 11) In Windows '95, if you shell to DOS when using SB on a high IRQ, then
- playback may stop! I've got no idea as to why this happens, but it seems
- to restore itself after loading another module (on a SB16)
-
- 12) In Windows '95, the program sometimes used to cause the computer to hang.
- This has NEVER happened since I specified full command line parameters.
-